Registry + Artifacts: Add usage table - #3057
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
📄 Preview this PR's docs ·
Updated 2026-08-20 18:52:04 UTC for deployment. |
Readability impactWord-weighted Flesch-Kincaid grade change across 6 changed pages: +0.1 (harder). Lower Flesch-Kincaid grade and higher reading ease both mean easier to read. This check is informational and never blocks a PR. Human readability
AI agent comprehensionRated 0-3 (higher is easier for an agent to parse and act on).
Curated-docs baseline median FK grade by type: conceptual 10.5, procedural 8.8, reference 9.4. |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Preview: https://wb-21fd5541-registry-limit-table.mintlify.site |
Knowledgebase navigation update
Generator warnings
|
| @@ -0,0 +1,12 @@ | |||
| | Dimension | Scope | Counting | Free | Pro | Enterprise | | |||
There was a problem hiding this comment.
these limits most likely will no affect on prem, not sure if we need to call that out or not
| | Linked versions per Registry Collection | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | | ||
| | Versions per artifact sequence | Per artifact sequence | Committed versions in one branch (sequence) | 1,000 | 10,000 | 50,000 | | ||
|
|
||
| An artifact *sequence* is a specific, versioned artifact in a project. For example, if you log an artifact named `model`, W&B creates a sequence called `model`. Each time you log a new version of that artifact, W&B creates a new version in the sequence: `model:v0`, `model:v1`, and `model:v2`. |
There was a problem hiding this comment.
In general, "Sequence" and "Portofolio" are internal terminology we use to distinguish project collections vs registry collections. With that, I would just maybe rename this to "Versions per project collection" and keep "Linked versions per registry collection"?
| | Linked versions per Registry Collection | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | | ||
| | Versions per artifact sequence | Per artifact sequence | Committed versions in one branch (sequence) | 1,000 | 10,000 | 50,000 | | ||
|
|
||
| An artifact *sequence* is a specific, versioned artifact in a project. For example, if you log an artifact named `model`, W&B creates a sequence called `model`. Each time you log a new version of that artifact, W&B creates a new version in the sequence: `model:v0`, `model:v1`, and `model:v2`. |
There was a problem hiding this comment.
also, here, a sequence isn't exactly a specific, versioned artifact. It is a collection of artifacts which is ordered / versioned
| | Dimension | Scope | Counting | Free | Pro | Enterprise | | ||
| | --- | --- | --- | --- | --- | --- | | ||
| | Registries| Organization | Registry projects in the organization | 5 | 25 | 250| | ||
| | Artifacts | Organization | Committed artifact versions across the whole organization | 100,000 | 5,000,000 | 100,000,000 | |
There was a problem hiding this comment.
Committed is an internal detail, here you can probably say Artifact versions across the whole org
| | --- | --- | --- | --- | --- | --- | | ||
| | Registries| Organization | Registry projects in the organization | 5 | 25 | 250| | ||
| | Artifacts | Organization | Committed artifact versions across the whole organization | 100,000 | 5,000,000 | 100,000,000 | | ||
| | Unique tags | Organization | Distinct tag definitions in the org | 1,000 | 1,000 | 10,000 | |
There was a problem hiding this comment.
| | Unique tags | Organization | Distinct tag definitions in the org | 1,000 | 1,000 | 10,000 | | |
| | Unique tags | Organization | Distinct tag definitions in the organization | 1,000 | 1,000 | 10,000 | |
| | Artifacts | Organization | Committed artifact versions across the whole organization | 100,000 | 5,000,000 | 100,000,000 | | ||
| | Unique tags | Organization | Distinct tag definitions in the org | 1,000 | 1,000 | 10,000 | | ||
| | Collections | Per Registry | Portfolios inside one registry | 50 | 250 | 5,000 | | ||
| | Linked versions per Registry Collection | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | |
There was a problem hiding this comment.
| | Linked versions per Registry Collection | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | | |
| | Linked versions | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | |
| | Unique tags | Organization | Distinct tag definitions in the org | 1,000 | 1,000 | 10,000 | | ||
| | Collections | Per Registry | Portfolios inside one registry | 50 | 250 | 5,000 | | ||
| | Linked versions per Registry Collection | Per Registry Collection | Distinct linked artifact versions in one registry collection | 500 | 1,000 | 2,500 | | ||
| | Versions per artifact sequence | Per artifact sequence | Committed versions in one branch (sequence) | 1,000 | 10,000 | 50,000 | |
There was a problem hiding this comment.
| | Versions per artifact sequence | Per artifact sequence | Committed versions in one branch (sequence) | 1,000 | 10,000 | 50,000 | | |
| | Artifact Versions | Per project collection | Versions in one project collection | 1,000 | 10,000 | 50,000 | |
Description
Adds:
Note that I decided to keep it as one table because artifacts and registry are heavily tied together + keeping separate include snippets is prone to drift.
Related issues